Skip to main content

This is a new service – your feedback will help us to improve it.

North Lincolnshire Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

South of Vicarage

reference
TPO7352
name
South of Vicarage
tree-preservation-order

undefined

Redbourne 1949
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-0.533154 53.484355,-0.533154 53.484372,-0.533160 53.484407,-0.533166 53.484424,-0.533183 53.484457,-0.533206 53.484489,-0.533236 53.484519,-0.533272 53.484546,-0.533292 53.484559,-0.533359 53.484592,-0.533436 53.484617,-0.533491 53.484629,-0.533519 53.484633,-0.533577 53.484639,-0.533606 53.484640,-0.533664 53.484639,-0.533721 53.484634,-0.533805 53.484618,-0.533831 53.484611,-0.533882 53.484593,-0.533950 53.484561,-0.533989 53.484535,-0.534006 53.484521,-0.534036 53.484491,-0.534061 53.484460,-0.534078 53.484426,-0.534084 53.484409,-0.534088 53.484392,-0.534091 53.484357,-0.534090 53.484340,-0.534082 53.484306,-0.534067 53.484272,-0.534057 53.484256,-0.534032 53.484224,-0.534017 53.484209,-0.533982 53.484181,-0.533963 53.484168,-0.533921 53.484145,-0.533873 53.484124,-0.533848 53.484115,-0.533796 53.484101,-0.533740 53.484090,-0.533712 53.484086,-0.533654 53.484081,-0.533596 53.484081,-0.533538 53.484085,-0.533481 53.484094,-0.533427 53.484106,-0.533401 53.484114,-0.533351 53.484132,-0.533306 53.484154,-0.533285 53.484166,-0.533247 53.484193,-0.533231 53.484207,-0.533202 53.484237,-0.533180 53.484269,-0.533164 53.484303,-0.533159 53.484320,-0.533154 53.484355)))
point
POINT (-0.533622 53.48436)
notes
entry-date
1949-09-13
start-date
1949-05-26
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve North Lincolnshire Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL